Added a comment: Workaround for default wanted content?
authornobodyinperson <nobodyinperson@web>
Mon, 21 Jul 2025 18:12:59 +0000 (18:12 +0000)
committeradmin <admin@branchable.com>
Mon, 21 Jul 2025 18:12:59 +0000 (18:12 +0000)
doc/todo/Setting_default_preferred_content_expressions/comment_4_c8a5f77b8a90524afb6bf44a8bde5975._comment [new file with mode: 0644]

diff --git a/doc/todo/Setting_default_preferred_content_expressions/comment_4_c8a5f77b8a90524afb6bf44a8bde5975._comment b/doc/todo/Setting_default_preferred_content_expressions/comment_4_c8a5f77b8a90524afb6bf44a8bde5975._comment
new file mode 100644 (file)
index 0000000..c57019c
--- /dev/null
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="nobodyinperson"
+ avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5"
+ subject="Workaround for default wanted content?"
+ date="2025-07-21T18:12:59Z"
+ content="""
+I am trying to work around this, but can't really find a solution. Any of the following for one-off overriding of the preferred content would help, but apparently something like this doesn't exist, right? One has to go through `git annex wanted . present`?
+
+- `git -c annex.wanted=present annex assist`
+- `GIT_ANNEX_WANTED=present git annex assist`
+- `git annex assist|sync --wanted=present`
+
+[[preferred_content]] and [[git-annex-common-options]] don't list anything obvious in that direction.
+
+An environment variable would be particularly great as that's easy to deploy globally.
+"""]]